Resynchronization + stock control

• Site (field STOFCY)

The storage site is initialized by default with the site linked to your function profile.

• All sites (field FCYALL)

Select this check box so the selected scripts are applied to all the stock sites.

• Category Start: (field TCLCODSTR)

Enter this field to select a range of categories. Specify the category corresponding to the selection start range.

• Category end: (field TCLCODEND)

Enter this field to select a range of categories. Specify the category corresponding to the selection end range.

• From product (field ITMREFSTR)

Enter this field to select a product or a range of products. Specify the reference of the product corresponding to the selection start range.

• To product (field ITMREFEND)

Enter the ending product number for the selection. Product ranges are used to restrict the report to these products only.

• Stock lines (field SYNSTO)

Select this check box to resynchronize the totals in the stock lines and trigger the purge of null stock lines. The calculation of allocated quantities is run in packing units (PAC) activated on potency-managed products.

• Quality checks (field SYNQLY)

Select this check box to:

• resynchronize the quality controls
• update the STOQLYH (quality control header) and STOQLYHD (quality control detail) files from the stock lines.

Different cases are possible.

Loop on STOQLYD:

• The system deletes a record in STOQLYD when in parallel there is no corresponding record in the STOQLYH and STOCK files.
• The system creates a new record STOQLYH when in parallel there is a record in STOCK.
• If a record exists in STOQLYD without corresponding record in the STOCK file but with a record in the STOJOU file, then the system sets the VALFLG (validation flag) field in STOQLYH to the value 2.
• If there is a corresponding record existing in STOQLYH and STOCK, the system verifies that the VALFLG field is set to 1 and readjusts the quantities between the STOCK and STOQLYD records.

Loop on STOCK:

• If no record exists in the STOQLYH and STOQLYD files, the QLYCTLDEM (analysis request) field in STOCK is reset to zero.
• A record in STOQLYD is created when an analysis request is referenced in STOCK and STOQLYH.
• Reciprocally, a record in STOQLYH is created when an analysis request is referenced in STOCK and STOQLYD. In parallel, the quantities in STOCK and STOQLYD are checked.
• The system readjusts the quantities between the STOCK and STOQLYH records when these already exist.

Loop on STOQLYH:

When no record exists in STOQLYD then the STOQLYH record is purged.

• Assemblies (field SYNBBY)

Select this check box to resynchronize the remaining quantity headings prior to a potential disassembly (the processing is run for all sites).

• Product-site totals (field SYNITV)

Select this check box to recalculate the site stock based on the stock lines of this site.

The processing compares the file of product-site totals (ITMMVT) to the other files:

• Comparison of the quantity with status A, Q, R in the ITMMVT file with respect to the STOCK file.
• Comparison of the reserved quantity in the ITMMVT file with respect to the STOCK file.
• Comparison of the quantities in transfer (in transit and transferred), the globally allocated quantities, the shortage quantities, the required quantities in the ITMMVT file with respect to the allocations file (STOALL).
• Comparison of the quantity on order in the ITMMVT file with respect to the ORDERS file.

In the first instance, the system deletes the old amounts (storing the old values). After comparing the files described above, the ITMMVT file is updated when a variance has been established. This leads to updating all stocks (reserved stock, allocated stock, stock in transfer...) in the ITMMVT table.

• Counts (field SYNCUN)

Check this box to resynchronize the stocks and trigger the purge of null stock lines.

The process verifies that the product-sites, stock lines and locations blocked for stock counts are correctly identified. If this is not the case, the hold flag and the list of stock count records concerned are reset to zero.

Additionally, the processing checks:

• the CUNLISSTA status in the CUNLISTE file,
• the CUNSSSSTA status in the CUNSESSION file.

If inconsistencies are detected, they are corrected and reported in the log file. For instance:

• For the CUNLISSTA status in the CUNLISTE file, this type of message is displayed:
  "Stock count status: list SSE-ASN0301111 INV-ASN0309000 modified! : 5 -> 4"
• For the CUNSSSSTA status in the CUNSESSION, this type of message is displayed:
  "Stock count status: session SSE-ASN0301111 modified! : 1 -> 2"

• Stock lots (field SYNLOT)

Select this check box to recalculate and update the stock by lot/site based on the stock lines of this site.
The processing consists in comparing the lot/site file (STOLOTFCY) to the stock file (STOCK). In case of variances, the STOLOTFCY lot file is the file which will be updated.

• FIFO cost and stock (field CSTCTL)

Select this check box to control the consistency between the quantity expressed in the stock and the quantity indicated in the FIFO stack for each product on the site.

The script compares the STOCOST file to the STOCK file.

When an anomaly is discovered, the error must be corrected manually.

• Single-lot (field FEACTL)

• Serial number (field SERCTL)

Select this check box to reconciliate stock lines and the related serial numbers.

• License plate number (field LPNCTL)

Select this check box to control the consistency of information relating to the License plate numbers: their status, location, management mode (single-lot or multi-lot), and all the information on their attached stock lines.

In some cases, the Resynchronization process updates the container. In contrast, specific errors are only reported in the log file because they require a manual intervention. To correct these errors, use the License plate number operations function.

The controls can be broken down as follows:

1/ Control on stock lines
If containers are associated to stock lines, these containers should not be associated with a location of the following categories:

• Subcontractor

• Customer

• Awaiting put-away, if the stock line is not fully assigned.

If it is, the resynchronization process breaks the link between the containers and the stock lines. The log file specifies the stock chrono counter and the updated license plate numbers.

2/ Control on the internal container license plate number

A - Status check: the container status must be 'Free' if no stock line is associated with it. The container status must be 'In stock' if at least one stock line is associated with it.
If an error occurs, the Resynchronization process automatically updates the status. A warning message indicates the changes carried out in the log file.

B - Checking the location category associated with the internal container: It must not be a ‘Subcontractor’ or ‘Customer’ category.
If an error occurs, the resynchronization process deletes the subcontractor or customer location if the container status is free.

C - Checking the consistency between the container location and the location of its associated stock lines: These locations must be identical.
If an error occurs, no update is performed but the inconsistent license plate number and the locations concerned are reported in the log file.

D - Checking the uniqueness of the location: A location may have multiple containers, but a container can only be on a single location.
If an error occurs, no update is performed but the inconsistent license plate number is reported in the log file.

E - Checking the single-product and single-lot compliance: If the container is single-product managed, the associated stock lines must be set to the same product code. The same goes in single-lot management.
If an error occurs, no update is performed but the license plate number that does not comply with this rule is reported in the log file.

• Reset QC frequency locks (field RAZFRE)

The use of this check box is technical; it responds to the following situation:

When the product is set up at the product-supplier level or at the product-site level in order to be subject to a periodic quality control, technical locks are managed by Enterprise Management on the ITMFACILIT and ITMBPS tables.

In the event of an incident (e.g.: power outage), these locks may not always be deleted. In this case, the frequency of the quality control is faulty and the quality control is never triggered.
Select this check box to delete these locks.